Oh, here's an interesting find from the demo output:

  Task-234 is done=False
   trace:
Stack for <Task pending name='Task-234' coro=<Broker._add_client() running at /home/alancoding/repos/dispatcher/dispatcher/brokers/socket.py:45> wait_for=<Future pending cb=[Task.task_wakeup()]> cb=[StreamReaderProtocol.connection_made.<locals>.callback() at /usr/lib64/python3.12/asyncio/streams.py:248]> (most recent call last):
  File "/home/alancoding/repos/dispatcher/dispatcher/brokers/socket.py", line 45, in _add_client
    line = await client.reader.readline()

It's right about where we expected it to be.

Again, I hit an issue where it will be difficult to move forward before #121 lands.

When running commands as dispatcherctl entrypoint (the ultimate point of this), it can hang waiting for a reply. (yes this means timeout isn't working)

The reply isn't coming because origin information is 0. This is, predictably, because the control.py module has not had its contract updated to the same as DispatcherMain. However, the PR 121 removes the need to copy this contract in the first place. So that's where this leaves us.

I figured out what it was. In asyncio, there are problems having parallel tasks both listening and writing to the same connection. This is roughly the same issue I hit with pg_notify. The solution is same in form, except for the multiple tasks for different clients.

I vetted the basic functionality with AWX and it's working so I'm going ahead with merge. Some code organizational issues are documented, but this isn't meant to be polished at this point.